Transporting business intelligence objects between business intelligence systems

ABSTRACT

A computer readable medium includes executable instructions to create a first export file that defines attributes and relationships associated with a first business intelligence object. A second export file that characterizes a second business intelligence object associated with the first business intelligence object is formed. The first export file and the second export file are combined into a composite export entity. The composite export entity is distributed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/303,039 filed Dec. 14, 2005 entitled “Apparatus And Method ForTransporting Business Intelligence Objects Between Business IntelligenceSystems,” which is incorporated herein by reference in its entirety.

BRIEF DESCRIPTION OF THE INVENTION

This invention relates generally to data storage and retrieval. Moreparticularly, this invention relates to a technique for extracting abusiness intelligence object from one business intelligence system anddeploying the business intelligence object in another businessintelligence system.

BACKGROUND OF THE INVENTION

Business Intelligence (BI) generally refers to software tools used toimprove enterprise decision-making, where an enterprise may be abusiness, government entity, foundation, and the like. These tools arecommonly applied to financial, human resource, marketing, sales,customer and supplier analyses. More specifically, these tools caninclude: reporting and analysis tools to present information; contentdelivery infrastructure systems for delivery and management of reportsand analytics; data warehousing systems for cleansing and consolidatinginformation from disparate sources; and data management systems, such asrelational databases or On Line Analytic Processing (OLAP) systems usedto collect, store, and manage raw data.

BI systems commonly process BI objects. A BI object is a software objectthat characterizes resources and data within a BI system. BI objects mayinclude schedules, users, servers, data sources, reports, documents,files (e.g., spread sheets, graphics, data), and the like. A BI objecttypically contains metadata characterizing itself and/or other entitieswithin a BI system. Metadata is information about information. Metadatatypically constitutes a subset or representative values of a larger dataset.

A BI object can include a metadata element, a data structure, or acombination of both. An example of a BI object that contains metadatacharacterizing other entities within a BI system is where a BI objectcharacterizes an associated file. For example, the associated file couldbe a report—itself a BI object. BI objects include data structures,e.g., an associated file including a report, etc., and metadataelements, e.g., a BI object characterizing a data structure.

Sometimes it is desirable to move a BI object from one system toanother, such as when developing content in a test system for deploymentin a production system, when providing example BI objects for import toa customer system, when upgrading between two versions of a system, whenmoving new versions of objects from one system to another, and whenbackup and versioning of objects. BI object movement can be accomplishedby having the source and target system simultaneously online and networkaccessible by a third system. In this solution, the third system exportsobjects from the source system, performs any required processing, andimports the objects into the target system. This solution is restrictivesince both systems must be running and the import tool must be able toaccess both systems via a network. In addition, this solution iscomplicated because one or both systems may be located behind firewallsand/or may be located in physically remote locations and/or differentnetworks. Furthermore, this solution can create a security risk as bothsystems may be accessible from a network.

Another problem is transporting third-party BI objects. New kinds of BIobjects may be created by third-parties and published to a proprietaryBI system. Frequently these new objects must be moved to other BIsystems, yet the BI system designers have no prior knowledge of thestructure of the BI objects. This problem can be resolved by re-writingthe import tool to understand every new kind of BI object. This solutionis restrictive since it is resource intensive and requires thecoordination between import tool developers and all third-party BIobject developers. Of course a system can be configured that does notsupport third-party BI objects. However, this solution restricts theextensibility of a BI system.

In view of the foregoing, it would be desirable to provide an improvedtechnique for moving BI objects from one system to another system.

SUMMARY OF THE INVENTION

The invention includes a computer readable medium with executableinstructions to create a first export file that defines attributes andrelationships associated with a first business intelligence object. Asecond export file that characterizes a second business intelligenceobject associated with the first business intelligence object is formed.The first export file and the second export file are combined into acomposite export entity. The composite export entity is distributed.

The invention also includes a computer readable medium with executableinstructions to receive a composite export file including a first exportfile that defines attributes and relationships associated with a firstbusiness intelligence object and a second export file that characterizesa second business intelligence object associated with the first businessintelligence object. The first business intelligence object and thesecond business intelligence object are merged into an object hierarchyof a target business intelligence system.

BRIEF DESCRIPTION OF THE FIGURES

The invention is more fully appreciated in connection with the followingdetailed description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 illustrates a computing system configured in accordance with anembodiment of the invention.

FIG. 2 illustrates processing operations associated with an exportprocess configured in accordance with an embodiment of the invention.

FIG. 3 illustrates processing operations associated with an importprocess configured in accordance with an embodiment of the invention.

FIG. 4 illustrates the processing of object dependencies in accordancewith an embodiment of the invention.

FIG. 5 illustrates the preservation of object hierarchies in accordancewith an embodiment of the invention.

FIG. 6 illustrates an overview of a system for transporting businessintelligence objects between business intelligence systems in accordancewith an embodiment of the invention.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a system 100 configured in accordance with anembodiment of the invention. The system 100 includes a centralprocessing unit 102 connected to a set of input/output devices 104 via abus 106. The input/output devices 104 include standard components, suchas keyboard, mouse, display, printer, and the like. Also connected tothe bus 106 is a network connection circuit 108, which providesconnectivity to a network (not shown). Thus, the system 100 may operatein a networked environment as either a client or a server. Alsoconnected to the bus 106 is a memory 110. The memory 110 storesexecutable instructions to implement operations of the invention. Inparticular, the memory stores executable instructions defining a BIobject export module 112 and/or executable instructions defining a BIobject import module 114.

FIG. 2 illustrates processing operations associated with one embodimentof a BI export module 112 configured in accordance with an embodiment ofthe invention. Initially, an export file is created for a BI object 200.For simplicity, the invention discusses the processing of one BI object.Naturally, the invention is also applicable to the processing ofmultiple BI objects. The BI object is an object that will be ported froma source system to a target system. The BI object is characterizedwithin an export file, which may be a text file or an Extensible MarkupLanguage (XML) file. The export file includes content associated withthe BI object that the target system will need to reconstruct the BIobject. The file structure used in accordance with an embodiment of theinvention allows the BI object to be ported in any number of ways.

By way of example, various types of BI objects may be utilized inaccordance with the invention, including:

user object—specifying a user

connections object—representing connections to a database

dynamic cascading prompt object—characterizing user prompts in a userinterface

glossary term object—representing a glossary term for an encyclopediaapplication

logon session object—representing information about a user logon session

relationship object—governing how objects relate to each other

report object—representing information about a report

file object—representing information about a file

Each kind of BI object may use a rules file. The rules file defines thestructure of the BI object. Thus, the rules file creates arepresentation of an object and allows for the reconstruction of theobject from its representation in the export file. The rules file ismeta-metadata, that is information about information on information. Inan embodiment where an object is characterized within an XML file. Therules file can be a XML Schema Definition (XSD) file. The use of rulesfiles allows for the importation and exportation of BI objects that weredesigned independently of the core business enterprise system. The useof rules files allows for more flexible code that can be updated in partby supplying new rules.

Below is an example of a rule file for a metadata element defined as“Name”. In this case the rule (a meta-metadata element) is expressed asXSD for a metadata element stored in XML.

<xs:element name=“Name”> <xs:complexType> <xs:simpleContent><xs:restriction base=“StringProperty”> <xs:attribute name=“nameID”type=“xs:string” use=“optional” fixed=“SI_NAME”/> </xs:restriction></xs:simpleContent> </xs:complexType> </xs:element>The rule includes tags specifying an element name, complex type,simpleContent, a restriction and an attribute name. Based upon thisrules file, an export file for a name defining a statement of accountmay be expressed as <io:Name>Statement of Account</io:Name>.

Next, inheritance, dependency and hierarchy information associated withthe BI object is characterized 202. The BI object dependencies areidentified. This may be implemented using the inheritance, dependencyand hierarchy information. Subsequently, the dependent BI object areretrieved 204. Each dependent BI object is parsed for additionaldependent BI objects. If additional dependent objects are found, thedependency and hierarchy information associated with these BI objectsare characterized.

Some BI objects require the presence of other objects in order tofunction. These dependencies may not be apparent to the end user who isexporting BI objects. The BI object export module 112 includesexecutable instructions to automatically identify and export informationabout objects on which the chosen object has a dependency. Thedependencies are reconstructed when the set of objects are imported intothe target system. This functionality ensures that the exported objectpreserves functionality when it is imported to a new system.

In one implementation, the BI object export module 112 includesexecutable instructions to identify any element in an object thatreferences another object. For example, an object may form part of adependency tree. In this case, the BI object export module 112progresses through the dependency tree until all dependent objects areidentified. For example, the BI object export module 112 may beconfigured to assume that elements of the following type are referencesto dependent objects: local identifiers and global identifiers. In thiscase, the objects with these identifiers will be exported. Preferably,the BI object export module 112 is programmable to specify an acceptabledepth of analysis into a dependency tree. If a dependent object cannotbe located within a system, the BI object export module 112 preferablynotes an error upon import. Optionally, the BI object export module 112is programmable to export only those BI objects needed for export. Forexample, the BI object export module 112 may time stamp a list ofobjects, but only export those objects that have been updated since thetime stamp.

FIG. 4 illustrates a source system in which object B within Folder A isdependent upon object F within Folder B. The object dependency betweenobjects B and F is identified. The composite export file includesinformation on these objects so that they may be constructed in thetarget system.

BI objects are organized into hierarchies. Hierarchies are another formof dependency. Hierarchies are important as they impact how the systeminteracts with the object, including: navigation through the set ofobjects, how security is applied to the object, how objects interactwith and affect the behavior of other objects, and whether the object isdisplayed in certain user interface pages.

FIG. 5 illustrates a source system with an object B dependent uponobject A. The BI object export module 112 notes this hierarchicaldependency and insures that the composite export file preserves thisdependency in the target system. In particular, when the object B isexported, it preserves its dependency on object A in the target system.Specifically, as shown in FIG. 5, when object B is imported into thetarget system, it is placed in the correct position in the targetsystem's hierarchy, even if the source and target system hierarchies arenot identical.

Security may also be considered a form of dependency. A user or usergroup has a set of rights on a BI object that controls what actions theuser can take with that object. Preferably, the BI object export module112 preserves these security settings when exporting the BI objects suchthat the reconstructed BI objects are secured in the same way for thesame user in the imported system. For example, a file that has beenmodified will not be imported. A user's security settings are preservedon export and are reapplied on import.

After the BI object dependency operations of block 204 are performed,domain specific identifiers for the BI object may be mapped to globalidentifiers 206. This operation supports the porting of a BI objectdeveloped by a third-party. Domain specific identifiers provide a meansfor uniquely identifying BI objects. Some types of BI object identifiersprovide unique identification within a single business enterprisesystem, while others provide unique identification globally across allbusiness enterprise systems. The BI object export module 112 performsany required conversions on these identifiers, such that they areguaranteed to be unique where required, but also so the relationshipsand dependencies between the BI objects are preserved. In particular,domain specific identifiers are mapped to global identifiers. Forexample, object identifications may be unique within a single cluster,while cluster object identifications are unique across a set ofclusters. Because object identifications are not valid in a new system,the BI object export module 112 may convert all object identificationsto cluster object identifications. Upon import, the target systemconverts cluster object identifications to domain specific objectidentifications.

Next, associated files that are required for the export operation areidentified and retrieved 208. Associated files include those files thatcharacterize objects that a BI object relies upon to operate correctly.Thus, these files include files that characterized dependent objects orhierarchical objects that are required for proper operation, asdiscussed above. That is, previous processing operations identifiedobjects related to a BI object that is to be exported. This operationidentifies and/or creates files that characterize the related objects.

A composite export file is created 210. Optionally, the export file andany associated files are compressed. The export file and associatedfiles may be combined into a single file prior to compression.Alternately, the export file and any associated files may be combinedinto a logical grouping of files after compression. Regardless of thetechnique used, combined files are referred to as a composite exportfile. The composite export file may be compressed via a lossless datacompression scheme such as run length encoding, e.g., ZIP, LZW, orHuffman encoding. Optionally, the composite export file is encrypted.The export file and the associated files can be encrypted prior to thecomposite export file's creation, or the composite export file itselfcan be encrypted.

Finally, the composite export file is distributed 212. The compositeexport file may be distributed in any number of ways, including thedownloading of the export file to the target system, sent by (secure)file transfer protocol, down or up loaded to a web resource, stored on acomputer readable medium and physically transported, or the emailing ofthe export file to the target system. For example, the composite exportfile may be sent by the BI object export module 112 to the networkconnection circuit 108 for delivery to a specified network computer.

FIG. 3 illustrates processing operations associated with a BI objectimport module 114. Initially, a composite export file is received 300.The composite export file may be received at any networked computer thatsupports the operations of the BI object import module 114. Alternately,the composite export file may be received at a different processoperating on the same machine that generated the composite export file.

The object or objects defined by the composite export file are thenreconstructed 302. Dependencies between the objects are then resolved304. Finally, the object or objects are placed in the appropriatehierarchical location or locations within the target system 306, such asshown in FIG. 5.

The invention can update objects in the target system as well as createnew ones. If the object being imported already exists in the targetsystem, then the BI object import module 114 will not replace theexisting object, but will optionally update it based on the contents ofthe new object. The export file can be used to specify whether an updateor over-write will occur or whether the object in the target system willtake precedence.

An existing object may be merged with a new object. The merged objectwill contain all the properties from both the existing and the newobject (i.e., no properties will be deleted), but the new object'sproperties will take precedence over the existing object's propertiesshould any differences exist. For example, consider an existing objectwith properties “a, b, c”. An object to be imported has properties “a′,x, y” (where a′ is a new version of property a). In this example, themerged object will have the properties a′, b, c, x, and y. Thisconversion process preserves all business intelligence meaning of theobject or set of objects, including security, metadata values,inheritance, relationships, and dependencies.

FIG. 6 illustrates an overview of a system for transporting businessintelligence objects between business intelligence systems in accordancewith an embodiment of the invention 600. A plurality of BI objects isshown in a first region (e.g., an object management server) 602. Asecond region (e.g., a file repository server) 604 stores a plurality offiles characterized by BI objects. The contents of these regions can befed into an importing/exporting engine 606 (e.g., a combination of theBI object export module 112 and BI object import module 114). The engine606 uses a series of rule files 608 to create a composite export file620. The export process takes data from the first region 602 and secondregion 604, processes the data in engine 606 and creates an export file620. The import process is the reverse.

The contents of the two regions are related. The first region 602 storesa plurality of BI objects. These objects contain the metadata on filesstored in the second region 604. The BI objects have associations,dependencies, and hierarchies, e.g., the tree with objects A, B, C andD. The second region 604 stores a plurality of associated filescharacterized by each BI object in the first region 602. The associatedfiles in the second region 604 are the data for the metadata in theobjects in the first region. As shown, the associated files in thesecond region 604 have no record of their hierarchy, instead they relyon the BI objects in the first region 603. For example, the tree withobjects A through D is paired with files A₁ through D₁, as shown byarrows 652 through 658. In some embodiments, the mapping between objectsand files in the two regions is not one to one. For example, object G inregion 602 has three files G₁ through G₃ in region 604, as shown witharrow 664. A file may also have many associated objects.

The types of files stored in the first region 604 include BIapplication, report, spread sheet, word processing, graphics, textdocument, data, and comma delimited files. The types of file stored inthe second region 604 include application specific files and documents,e.g., BI application files. For example this can include files anddocuments specific to Business Objects Web Intelligence™, CrystalReports™, Business Objects OLAP Intelligence™, Business Objects WebIntelligence™, Business Objects Desk Intelligence™ or Business ObjectsEnterprise™. Another type of file stored in the second region 604includes program files, e.g., binary encoded computer instructions.

The processing operations of FIGS. 2 and 3 occur in theimporting/exporting engine 606. The engine 606 uses a series of rulefiles 608. The rule files 608 can be a collection of meta-metadata,e.g., XSD files for XML files. The rule files permit the codeimplementing the importing/exporting engine 606 to be flexible, e.g.,new type of object can easily be handed by parsing the associated rules.

The composite export file 620 is created by the importing/exportingengine 606. File 620 contains an export file 622 for the characterizingthe BI objects for the associated files 624. The associated files in thecomposite export file 620 are being exported from, or imported to,region 604. The associated files may have their file names changed. Forexample, a file may be labeled “ID.NNN”, where “ID” is the globalidentifier for the particular file and “NNN” is the number of theparticular file, e.g., for the case where more than one file of a typeare exported. A file may have more than one extension. Those skilled inthe art will recognize a number of advantages associated with theinvention. For example, the invention provides a technique for movingbusiness objects, which does not require multiple systems to besimultaneously operative and communicative. Rather, the export entitiesof the invention can be created at one point in time and then beutilized at another point in time. If the export entity is alreadyexported, the source entity need not even be operative when the exportentity is utilized by the target system. The export entity of theinvention easily traverses firewalls and other networked components. Inaddition, the identifier mapping techniques of the invention support thedeployment and porting of third-party objects within a BI system.

An embodiment of the present invention relates to a computer storageproduct with a computer-readable medium having computer code thereon forperforming various computer-implemented operations. The media andcomputer code may be those specially designed and constructed for thepurposes of the present invention, or they may be of the kind well knownand available to those having skill in the computer software arts.Examples of computer-readable media include, but are not limited to:magnetic media such as hard disks, floppy disks, and magnetic tape;optical media such as CD-ROMs, DVDs and holographic devices;magneto-optical media; and hardware devices that are speciallyconfigured to store and execute program code, such asapplication-specific integrated circuits (“ASICs”), programmable logicdevices (“PLDs”) and ROM and RAM devices. Examples of computer codeinclude machine code, such as produced by a compiler, and filescontaining higher-level code that are executed by a computer using aninterpreter. For example, an embodiment of the invention may beimplemented using Java, C++, or other object-oriented programminglanguage and development tools. Another embodiment of the invention maybe implemented in hardwired circuitry in place of, or in combinationwith, machine-executable software instructions.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the invention.However, it will be apparent to one skilled in the art that specificdetails are not required in order to practice the invention. Thus, theforegoing descriptions of specific embodiments of the invention arepresented for purposes of illustration and description. They are notintended to be exhaustive or to limit the invention to the precise formsdisclosed; obviously, many modifications and variations are possible inview of the above teachings. The embodiments were chosen and describedin order to best explain the principles of the invention and itspractical applications, they thereby enable others skilled in the art tobest utilize the invention and various embodiments with variousmodifications as are suited to the particular use contemplated. It isintended that the following claims and their equivalents define thescope of the invention.

The invention claimed is:
 1. A non-transitory computer readable medium,comprising executable instructions to: create a first export file thatdefines attributes and relationships associated with a first businessintelligence object in a source system; form a second export file thatcharacterizes a second business intelligence object associated with thefirst business intelligence object, the presence of the second businessintelligence object being required by the first business intelligenceobject to function; combine, using a rule file associated with the firstbusiness intelligence object and a rule file associated with the secondbusiness intelligence object, the first export file and the secondexport file into a composite export entity that preserves dependenciesbetween the first business intelligence object and the second businessintelligence object within a hierarchy of business intelligence objects,wherein each rules file comprises meta-metadata characterizing arepresentation of the corresponding business intelligence object thatallows for the reconstruction of the corresponding object from itsrepresentation in the composite export entity; and distribute thecomposite export entity to a target system so that the first businessintelligence object and the second business intelligence object can beinserted into an object hierarchy within the target system that is notidentical to an object hierarchy in the source system, the distributioncomprising one or more of: downloading the composite export entity to atarget system, sending the composite export entity by file transferprotocol, downloading or uploading the composite export entity to a webresource, storing the composite export entity to a computer readablemedium, or emailing the composite export entity to the target system;wherein: the composite export entity is distributed by one or more of:downloading the composite export entity to a target system, sending thecomposite export entity by file transfer protocol, downloading oruploading the composite export entity to a web resource, storing thecomposite export entity to a computer readable medium, or emailing thecomposite export entity to the target system; the composite exportentity further preserves security settings for at least one of the firstbusiness intelligence object and the second business intelligenceobject, the security settings defining what actions a user can take withthe corresponding business intelligence object.
 2. The non-transitorycomputer readable medium as in claim 1, wherein the attributes andrelationships associated with the first business intelligence object aredefined using inheritance, dependency, and hierarchy informationassociated with the first business intelligence object.
 3. Thenon-transitory computer readable medium as in claim 1, wherein thecomposite export entity maps a first identifier for the first businessintelligence object in a source system to a global identifier, theglobal identifier being used by a target system using the compositeexport entity to map to a second identifier for the businessintelligence object for the target system.
 4. The non-transitorycomputer readable medium as in claim 1, wherein at least a portion ofthe composite export entity is encrypted.
 5. A non-transitory computerreadable medium, comprising executable instructions to: receive, by atarget system from a source system, a composite export entity, thecomposite export entity being generated by: creating a first export filethat defines attributes and relationships associated with a firstbusiness intelligence object; forming a second export file thatcharacterizes a second business intelligence object associated with thefirst business intelligence object, the presence of the second businessintelligence object being required by the first business intelligenceobject to function; combining the first export file and the secondexport file into a composite export entity that preserves dependenciesbetween the first business intelligence object and the second businessintelligence object within a hierarchy of business intelligence objects;and reconstruct, by the target system, the first business intelligenceobject and the second business intelligence object by inserting thefirst business intelligence object and the second business intelligenceobject into an object hierarchy within the target system that is notidentical to an object hierarchy in the source system; wherein: thecomposite export entity is distributed by one or more of: downloadingthe composite export entity to a target system, sending the compositeexport entity by file transfer protocol, downloading or uploading thecomposite export entity to a web resource, storing the composite exportentity to a computer readable medium, or emailing the composite exportentity to the target system; the composite export entity furtherpreserves security settings for at least one of the first businessintelligence object and the second business intelligence object, thesecurity settings defining what actions a user can take with thecorresponding business intelligence object.
 6. The non-transitorycomputer readable medium as in claim 5, wherein the reconstructingcomprises: respectively placing the first business intelligence objectand the second business intelligence object into locations within ahierarchical location or locations within the target system as specifiedby the composite export entity.
 7. The non-transitory computer readablemedium as in claim 5, wherein the first export file is generated usingrules associated with the first business intelligence object, the rulesdefining a structure of the first business intelligence object to allowfor the reconstruction of the first business intelligence object in atarget system accessing the composite export entity.
 8. Thenon-transitory computer readable medium as in claim 5, wherein theattributes and relationships associated with the first businessintelligence object are defined using inheritance, dependency, andhierarchy information associated with the first business intelligenceobject.
 9. The non-transitory computer readable medium as in claim 5,wherein the composite export entity maps a first identifier for thefirst business intelligence object in a source system to a globalidentifier, the global identifier being used by a target system usingthe composite export entity to map to a second identifier for thebusiness intelligence object for the target system.
 10. Thenon-transitory transitory computer readable medium as in claim 5,wherein at least a portion of the composite export entity is encrypted.11. A non-transitory computer readable medium, comprising executableinstructions to: access a composite export entity, the composite exportentity being generated by: creating a first export file that definesattributes and relationships associated with a first businessintelligence object in a source system; characterizing inheritance,dependency, and object hierarchy information for the first businessintelligence object; retrieving objects in the source system upon whichthe first business intelligence object depends including a secondbusiness intelligence object; identify a rule file associated with thefirst business intelligence object, wherein the first businessintelligence object is further characterized by metadata of the rulefile; forming a second export file that characterizes a second businessintelligence object associated with the first business intelligenceobject, the presence of the second business intelligence object beingrequired by the first business intelligence object to function;combining the first export file and the second export file into thecomposite export entity such that the composite export entity preservesdependencies between the first business intelligence object and thesecond business intelligence object within a hierarchy of businessintelligence objects; and distribute the composite export entity to atarget system so that the first business intelligence object and thesecond business intelligence object can be inserted into an objecthierarchy within the target system that is not identical to an objecthierarchy in the source system.
 12. The non-transitory computer readablemedium as in claim 11, wherein the composite export entity isdistributed by one or more of: downloading the composite export entityto the target system, sending the composite export entity by filetransfer protocol, downloading or uploading the composite export entityto a web resource, storing the composite export entity to a computerreadable medium, or emailing the composite export entity to the targetsystem.
 13. The non-transitory computer readable medium as in claim 11,wherein: the composite export entity further preserves security settingsfor at least one of the first business intelligence object and thesecond business intelligence object, the security settings defining whatactions a user can take with the corresponding business intelligenceobject; and the composite export entity maps a first identifier for thefirst business intelligence object in a source system to a globalidentifier, the global identifier being used by a target system usingthe composite export entity to map to a second identifier for thebusiness intelligence object for the target system.